Trust management (information system)

In information system and information technology, trust management is an abstract system that processes symbolic representations of social trust, usually to aid automated decision-making process. Such representations, e.g. in a form of cryptographic credentials, can link the abstract system of trust management with results of trust assessment. Trust management is popular in implementing information security, specifically access control policies.

The concept of trust management has been introduced by Blaze[1] to aid the automated verification of actions against security policies. In this concept, actions are allowed if they demonstrate sufficient credentials, irrespective of their actual identity, separating symbolic representation of trust from the actual person.

Trust management can be best illustrated through the everyday experience of tickets. One can buy a ticket that entitles him e.g. to enter the stadium. The ticket acts as a symbol of trust, stating that the bearer of the ticket has paid for his seat and is entitled to enter. However, once bought, the ticket can be transferred to someone else, thus transferring such trust in a symbolic way. At the gate, only the ticket will be checked, not the identity of a bearer.

Overview

Trust management can be seen as a symbol-based automation of social decisions related to trust[2], where social agents instruct their technical representations how to act while meeting technical representations of other agents. Further automation of this process can lead to automated trust negotiations (e.g. see Winslett[3]) where technical devices negotiate trust by selectively disclosing credential, according to rules defined by social agents that they represent.

Web Services Trust Language (WS-Trust)[4] brings trust management into the environment of web services. The core proposition remain generally unchanged: the Web Service (verifier) is accepting a request only if the request contains proofs of claims (credentials) that satisfy the policy of a Web Service.

It is also possible to let technical agents monitor each others' behaviour and respond accordingly by increasing or decreasing trust. Such systems are collectively called Trust-Based Access Control (TBAC)[5] and their applicability have been studied for several different application areas.[6]

An alternative view on trust management[7] questions the possibility to technically manage trust, and focuses on supporting the proper assessment of the extent of trust one person has in the other.

References

  1. ^ Blaze, M. et al. (2003) "Experience with the KeyNote Trust Management System: Applications and Future Directions." Proc. of First Int. Conf. on Trust Management iTrust 2003. Springer-Verlag LNCS 2692, pp. 284-300.
  2. ^ Cofta, P. (2007) Trust, Complexity and Control. Confidence in a Convergent World. J Wiley.
  3. ^ Winslett, M. (2003) An Introduction to Trust Negotiations. In: P. Nixon and S. Terzis (eds.): Trust Management 2003, LNCS 2692, pp. 275-283.
  4. ^ Anderson, S. et al. (2005) Web Services Trust Language (WS-Trust).
  5. ^ Dimmock, N., Bacon, J., Ingram, D., and Moody. K. (2005) Risk Models for Trust-Based Access Control (TBAC). In: P. Herrmann (ed): iTrust2005, LNCS 3477, pp. 364-371
  6. ^ Adams, W. J., and Davis IV, N. J. (2005) "Towards a Decentralized Trust-Based Access Control System for Dynamic Collaboration." Proc. of the 2005 IEEE Workshop on Information Assurance and Security.
  7. ^ Josang, A., Keser, C., and Dimitrakos, T. (2005) "Can We Manage Trust?" In: P. Herrmann et al. (Eds.): iTrust 2005, LNCS 3477, pp. 93-107.